fix(changesets): remove peer deps - #1050

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
api-docs-tooling	Error		Aug 23, 2026 4:11pm

🚀 Deploying Preview to Cloudflare 🚀

Preview Deployments by commit

⚠️ JUnit XML file not found

The CLI was unable to find any JUnit XML files to upload.
For more help, visit our troubleshooting guide.

api-links Generator

Performance estimate _{(single CI run)}

• Generation time: 23.1% slower (1.04 s → 1.28 s)
• Peak memory: 2.3% lower (366.38 MB → 358.09 MB)

legacy-html Generator

Performance estimate _{(single CI run)}

• Generation time: 6.3% slower (19.90 s → 21.15 s)
• Peak memory: 5.6% higher (2.26 GB → 2.39 GB)

legacy-json Generator

Performance estimate _{(single CI run)}

• Generation time: 8.1% slower (7.81 s → 8.44 s)
• Peak memory: 0.6% higher (1.79 GB → 1.80 GB)

llms-txt Generator

Performance estimate _{(single CI run)}

• Generation time: 2.4% faster (8.49 s → 8.29 s)
• Peak memory: 2.9% higher (1.78 GB → 1.84 GB)

orama-db Generator

Performance estimate _{(single CI run)}

• Generation time: 14.3% slower (8.61 s → 9.84 s)
• Peak memory: 0.5% lower (1.81 GB → 1.80 GB)

web Generator

Output size: 1 file changed · net +210.00 B

Performance estimate _{(single CI run)}

• Generation time: 1.0% slower (85.12 s → 85.95 s)
• Peak memory: 1.7% higher (5.23 GB → 5.32 GB)

We need peer deps since without them, certain package managers (e.g. pnpm) will not link the dependencies to the core package.

We need peer deps since without them, certain package managers (e.g. pnpm) will not link the dependencies to the core package.

But shouldn't be the opposite? the other packages peerDepending on the core package?

The other dependencies have a required dependency of core, since they cannot function without them. Core has an optional peer dep, since it can function without them, but should they be installed, they need to be within this version range and a dep of core

The other dependencies have a required dependency of core, since they cannot function without them. Core has an optional peer dep, since it can function without them, but should they be installed, they need to be within this version range and a dep of core

Right but I feel we are creating cyclically peerDeps core depends on their downstream [...]

(maybe I am misunderstanding the implications of core having downstream deps depending on it as peerDeps)

It looks cyclic if you count peer edges, but it's an acyclic install graph, so this is an "intentional" semi-cycle (so-to-speak). core needs the peer declaration so pnpm resolves the optional packages into core's node_modules context.